System on chip fault detection

ABSTRACT

The invention relates to a method for fault identification in a System-on-Chip (SoC) consisting of a number of IP cores, wherein each IP core is a fault containment unit, and where the IP cores communicate with one another by means of messages via a Network-on-Chip, and wherein an excellent IP core provides a TRM (Trusted Resource Monitor), wherein a faulty control message which is sent from one non-privileged IP core to another non-privileged IP core is identified and projected by an (independent) fault container unit, as a result of which this faulty control message cannot cause any failure of the message receiver.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/383011 filed Feb. 2, 2012, which application was a 35 U.S.C. 371national stage application corresponding to PCT/AT2010/000248 filed Jul.7, 2010, which itself claims priority to Document Reference No. A1077/2009 filed on Jul. 9, 2009 in Austria. Each of the above-referenceddocuments is incorporated by reference herein.

FIELD OF THE INVENTION

The present invention relates to a method and to a device for improvingthe reliability of a system on chip in an embedded computer system.

The invention in particular relates to a method for detecting errors ina system on chip (SoC) comprising a number of IP cores, wherein each IPcore is a fault containment unit and wherein the IP cores communicatewith each other via a network on chip by means of messages, and whereinan outstanding IP core implements a trusted resource monitor (TRM).

BACKGROUND

A system on chip (SoC) is a system in which the majority of systemfunctions are integrated on a single piece of silicon. According toPollack's rule (Borkar, S. (2007) Thousand-Core Chips, A TechnologyPerspective, Proc. of the 44.sup.th ACM IEEE Design AutomationConference, p. 746-749, ACM Press, New York), powerful SoCs are composedof a number of IP cores that communicate via a network on chip. An IPcore is a hardware/software component that fulfills a predefinedfunction. IP cores can communicate either by the access of the IP coresto a common memory or by means of messages. The application PCT/AT2009/00207 presents an SoC architecture in which the IP corescommunicate exclusively by means of messages.

SUMMARY OF THE INVENTION

It is the object of the present invention to prevent a faulty IP core ofan SoC to cause another IP core that is not directly affected by theerror from failing.

It is therefore the object of the present invention to prevent an errorof an IP core from propagating to another IP core that is not directlyaffected by the error in a system on chip (SoC) in which a plurality ofcomponents (IP cores) communicate exclusively by means of messages. Thisobject is achieved in that a faulty control message, which is sent froma non-privileged IP core to another non-privileged IP core, is detectedand discarded by a fault containment unit (that is independent bydefinition), so that this faulty control message cannot cause failure ofthe message receiver.

Any message of an IP core that may trigger a failure of another IP corecan be checked, and optionally discarded, by a third IP core so as toprevent this faulty message being sent by a faulty IP core fromeffecting the failure of another IP core.

Special advantages are attained when each control message, which is tobe sent by a non-privileged IP core to another non-privileged IP core,is first sent to a third IP core, wherein this third IP core checks themessage, and wherein the message is forwarded by this third IP core tothe intended final receiver if the message is not faulty.

The checking IP core can classify a message as faulty if the evaluationof an assertion known a priori to the checking IP core has the value‘faulty’.

The third IP core is advantageously the TRM.

It is further advantageous for the TRM to forward messages only from asender that is authorized to send a control message to the IP corelisted in the message.

In addition, it may be provided that only the TRM can send a controlmessage to the technology-dependent interface (TII) of a non-privilegedIP core.

It is useful if each control message must be sent to the TII of an IPcore.

It may also be provided that at least three messages, each from adifferent IP core, must be sent to the TRM within a predefined timeinterval, and the receiving TRM checks whether at least two of the threemessages contain the same command, before this message is forwarded tothe TII of the addressed IP core.

It may further be provided that at least three messages, each from adifferent SoC, must be sent to the TRM within a predefined timeinterval, and the receiving TRM checks whether at least two of the threemessages contain the same command, before this message is forwarded tothe TII of the addressed IP core.

It is useful for the functions of the privileged subsystem, whichcomprises the TRM, the network on chip and the network interfaces, to besafeguarded by error-correcting codes.

The invention further relates to a device for carrying out a methoddescribed above, wherein one or more, or all, method steps are performeddirectly in the hardware of the SoC.

The aforementioned object and other novel properties of the presentinvention will be described in the accompanying drawings.

DESCRIPTION OF THE DRAWINGS

FIG. 1 shows the design of a system on chip (SoC).

FIG. 2 shows the structure of an IP core of an SoC.

FIG. 3 shows the transmission of a control message from an IP core toanother IP core of an SoC.

DETAILED DESCRIPTION

The following section shows an implementation of the novel method basedon a possible example of an SoC comprising eight IP cores.

FIG. 1 shows an SoC 100 comprising the eight IP cores 111, 112, 113,114, 115, 116, 117 and 118. These eight IP cores can exchange messagesvia a network on chip 101. Each IP core, for example IP core 114, isconnected to the NoC 101 via a network interface (NI) 102. One of theseeight IP cores, for example IP core 111, is a privileged IP core, whichis referred to as the trusted resource monitor (TRM), while theremaining seven IP cores 112, 113, 114, 115, 116, 117 and 118 arenon-privileged IP cores. The TRM 111, the network on chip 101 and theeight network interfaces 102 form the privileged subsystem of the SoC100. An error in this privileged subsystem can result in failure of theentire SoC. According to the invention, the functions of the privilegedsubsystem should thus be safeguarded by special error protectionmeasures, such as the use of error-correcting codes, for example.Appropriate error-correcting codes can detect and correct transient andpermanent hardware errors in the privileged system.

Each of the seven non-privileged IP cores forms a dedicated faultcontainment unit (FCU) (Kopetz, H. (1997). Real-Time Systems, DesignPrinciples for Distributed Embedded Applications; ISBN: 0-7923-9894-7.Boston. Kluwer Academic Publishers.), which is to say the consequencesof a random software error or hardware failure within a non-privilegedIP core can directly interfere only with the functions of the respectiveIP core, however they can affect the functions of the other IP coresonly indirectly by way of faulty messages. If it is possible to detectand discard faulty messages, the indirect consequences of an IP coreerror cannot propagate. PCT/AT 2006/00278 describes an architecture inwhich time errors of IP core messages are detected and discarded by theprivileged network interface (NI) 102 of the NoC 101. According toPCT/AT 2009/00207 (WO 2009/140707), only the TRM 111 is allowed to writetime parameters to the NI 102 so as to prevent a faulty IP core fromindependently modifying the transmission parameters of a message. Themethod as described in PCT/AT 2006/00278, however, does not preventcontrol messages with incorrect content from being sent from anon-privileged faulty IP core to the other non-privileged IP cores.

FIG. 2 shows the design of a non-privileged IP core, for example IP core114. This IP core has four external interfaces: 211, 212, 213 and 122.The three message interfaces 211, 212 and 213 are connected to thenetwork interface (NI) 102 of FIG. 1. The interface 122 is a localinterface of the IP core, via which a connection to the exterior of theSoC 100 is implemented. This interface 122 can, for example, be aninput/output network (for example a CAN network) or a wirelessconnection to the surroundings of the SoC 100.

The message interface 211 is referred to here as the linking interface(LIF) of the IP core 114. The services of the IP core 114 are offered tothe seven other IP cores of the SoC 100 via the LIF 211.

The message interface 212 is referred to here as thetechnology-dependent interface (TDI), which allows the maintenancetechnician to communicate with the internal functions of the IP core114. Because the format and the content of these TDI messages depend onthe specific implementation technology of the IP core, this interface isimplementation-dependent.

The message interface 213 is referred to here as thetechnology-independent interface (TDI). The configuration and the flowcontrol of the IP core 114 are implemented via this TII 213 by means ofcontrol messages. A control message is a message that controls the flowof the computation in an IP core. For example, a hardware reset of theentire IP core 114 is prompted by means of control messages, or thestart of a program execution or scheduling of a program execution of theIP core 114 is ordered. Moreover, the configuration or a reconfigurationof the SoC can be initiated by means of control messages. A faultycontrol message that is sent to the TII of the IP core may bring aboutthe failure of the IP core 114, for example when during the correctoperation of the IP core 114 suddenly a faulty hardware reset message isreceived at the TII 213. FIG. 2 also shows the inner design of the IPcore 114. The IP core hardware, which carries out the software loaded inthe IP core 114, is located at the lowest level 201. The IP coreinternal operating system is located on the next level 202, and the IPcore internal middleware is located on the level 203. Finally, theapplication software is located on level 204. The IP core internalinterface 214 between the middleware 203 and the application software204 is referred to as the application program interface (API) 214. Themessages that are received via the TII 213 communicate either directlywith the IP core hardware 201 (for example a reset message), with theoperating system 202 (for example a control message for scheduling aprocess), or the middleware 203, however not with the applicationsoftware 204. The application software of a non-privileged IP core isthus not able to detect faulty control messages that arrive via the TII213.

FIG. 3 shows the transmission of a control message to the TII of anon-privileged IP core. If, for example, the IP core 115 wants to send areset message 140 to the IP core 116, according to the invention it mustfirst send this message 140 to an independent third IP core, the TRM111. The TRM 111 checks whether the message 140 is faulty. This check iscarried out based on assertions that must be known a priori to the TRM.These assertions can relate to the state of the overall system, to theidentity of the sender, the time of the message and the content of themessage. If all assertions evaluated by the TRM are correct, the TRMsends the reset message 141 to the TII of the IP core 115. According tothe invention, the architecture must assure that only the (privileged)TRM 111 is in a position to send messages to the TII of a non-privilegedIP core. The implementation of a non-privileged IP core must assure thatcontrol messages (such as the reset message, for example) that couldresult in failure of an IP core can be received only via the TII. It istherefore not possible according to the invention for a non-privilegedIP core to directly send a control message to another non-privileged IPcore.

In a security-relevant system, the fault detection of the controlmessages by means of assertions may be considered to be insufficient. Insuch a system, three parallel operating IP cores must compute thecontrol commands, which are embedded in the control messages. The TRMcompares these three control messages and does only forward acorresponding message to the TII of the receiver, if at least two ofthese messages are identical. This masks any error in one of the threesending IP cores. In highly reliable systems, these three parallelcontrol messages must originate from three independent SoCs so as toprevent common mode failure that may occur within an individual SoC.

The present invention significantly improves the reliability of an SoCbecause it prevents a faulty IP core from causing the failure of anotherIP core. Fault detection in the receiving IP core is not useful becausethe receiving IP core cannot correctly perform its own fault detectionin the event of failure.

The specific implementation of the invention described here constitutesonly one of many implementation options of the present invention.

1. A system on chip (SoC) comprising: a number of non-privileged IP cores configured to communicate using messages via a network on chip, each non-privileged_IP core being a fault containment unit, and a privileged IP core, wherein a faulty control message that is sent from a non-privileged IP core to another non-privileged IP core is detected and discarded by the trusted IP core so that this faulty control message cannot cause failure of the message receiver.
 2. The SoC of claim 1, wherein: each control message sent by a non-privileged IP core to another non-privileged IP core is first sent to the privileged IP core, and the privileged IP core checks the message, and the message is forwarded by the privileged IP core to the intended final receiver when the message is not faulty.
 3. The SoC of claim 1 wherein the privileged IP core can classify a message as faulty when the evaluation of an assertion known a priori to the checking IP core has the value ‘faulty’.
 4. The SoC of claim 1, wherein the privileged IP core implements a Trusted Resource Monitor (TRM).
 5. The SoC of claim 1, wherein the privileged IP core forwards messages only from a sender that is authorized to send a control message to the IP core listed in the message.
 6. The SoC of claim 1, wherein: the non-privileged IP cores include a technology-dependent interface (TII); and only the TRM can send a control message to the technology-dependent interface (TII) of a non-privileged IP core.
 7. The SoC of claim 6, wherein each control message must be sent to the TII of a non-privileged IP core.
 8. The SoC of claim 7, wherein at least three messages, each from a different non-privileged IP core, must be sent to the privileged IP core within a predefined time interval, and the receiving privileged IP core checks whether at least two of the three messages contain the same command, before this message is forwarded to the TII of the addressed non-privileged IP core.
 9. The SoC of claim 8, wherein at least three messages, each from a different SoC, must be sent to the privileged IP core within a predefined time interval, and the receiving privileged IP core checks whether at least two of the three messages contain the same command, before this message is forwarded to the TII of the addressed non-privileged IP core.
 10. The SoC of claim 1, wherein the functions of the privileged subsystem, which comprises the privileged IP core, the network on chip and the network interfaces, are safeguarded by error-correcting codes. 